home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group94a.txt
/
000045_icon-group-sender _Wed Feb 16 14:23:37 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-08-19
|
1KB
Received: by cheltenham.cs.arizona.edu; Wed, 16 Feb 1994 15:39:16 MST
Date: Wed, 16 Feb 94 14:23:37 CST
From: jeffery@ringer.cs.utsa.edu (Clinton L. Jeffery)
Message-Id: <9402162023.AA10013@ringer.cs.utsa.edu.sunset>
To: kf8nh@kf8nh.ampr.org
Cc: icon-group@cs.arizona.edu
In-Reply-To: (Brandon S. Allbery's message of 12 Feb 94 18:59:50 GMT <1994Feb12.185950.447@kf8nh.wariat.org>
Subject: wishing for an Icon-like embedded language
Content-Length: 629
Status: R
Errors-To: icon-group-errors@cs.arizona.edu
Brandon Allbery writes:
> The biggest problem here is maintaining separate execution contexts for all
> clients. For the Prolog one I didn't need to; it was essentially a "Prolog
> database server" which arbitrated access to a common rulebase.
Well, the Icon interpreter has code (under yet another #ifdef that is turned
off by default) that supports separate execution contexts. In fact, if we
could just settle on a few network interface functions, y'all could almost
write this heyah suhver y'all are talkin about in Ahcon.
Clint Jeffery
jeffery@ringer.cs.utsa.edu
Deep in the heart of Texas, no one can hear you scream.